Back to overview

PHOENIX CONTACT: Vulnerability in ProConOS/ProConOS eCLR SDK and MULTIPROG Engineering tool

VDE-2022-026
Last update
05/22/2025 15:03
Published at
06/21/2022 07:16
Vendor(s)
Phoenix Contact GmbH & Co. KG
External ID
VDE-2022-026
CSAF Document

Summary

ProConOS/ProConOS eCLR insufficiently verifies uploaded data.

Impact

The identified vulnerability allows attackers uploading logic with arbitrary malicious code oncehaving access to the communication to products that are utilizing ProConOS/ProConOS eCLR.Attackers must have network or physical controller access to exploit this vulnerability. Thisvulnerability affects all versions of ProConOS/ProConOS eCLR and MULTIPROG from PhoenixContact Software (formerly KW-Software).

Affected Product(s)

Model no. Product name Affected versions
MULTIPROG vers:all/* MULTIPROG vers:all/*
ProConOS eCLR vers:all/* ProConOS eCLR vers:all/*
ProConOS vers:all/* ProConOS vers:all/*

Vulnerabilities

Expand / Collapse all

Published
09/22/2025 14:57
Weakness
Insufficient Verification of Data Authenticity (CWE-345)
Summary

An unauthenticated, remote attacker could upload malicious logic to the devices based on ProConOS/ProConOS eCLR in order to gain full control over the device.

References

Mitigation

Manufacturers using ProConOS/ProConOS eCLR in their automation devices are advised tocheck their implementation and may publish an advisory according to their product.
Users of automation devices utilizing ProConOS/ProConOS eCLR in their automation systemsmay check if their application requires additional security measures like an adequate defense–in-depth networking architecture, the use of virtual private networks (VPNs) for remote access,as well as the use of firewalls for network segmentation or controller isolation.
Users should check their manufacturers security advisories for more adequate informationaccording to their dedicated device.
Users should ensure that the logic is always transferred or stored in protected environments.This is valid for data in transmission as well as data in rest. Connections between theEngineering Tools and the controller must always be in a locally protected environment orprotected by VPN for remote access. Project data shouldn't send as a file via e-mail or othertransfer mechanisms without additional integrity and authenticity checks.Project data should save in protected environments only.
Generic information and recommendations for security measures to protect network-capabledevices can be found in the application note.

Revision History

Version Date Summary
1 06/21/2022 07:16 Initial revision.
2 05/22/2025 15:03 Fix: added distribution, quotation mark